From: Ihmig@tu-harburg.d400.de (Simon Ihmig)
To: mui@sunsite.Informatik.RWTH-Aachen.DE (MUI Mailing List)
Subject: Memory loss report
Message-Id: <511.6685T1200T334@tu-harburg.d400.de>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Mailer: THOR 2.22 (Amiga;TCP/IP) *UNREGISTERED*
Lines: 22
Resent-Message-Id: <"mzWuL.0.052.pugUn"@sunsite>
Resent-From: mui@sunsite.Informatik.RWTH-Aachen.DE
Reply-To: mui@sunsite.Informatik.RWTH-Aachen.DE
X-Mailing-List:  archive/latest/1126
X-Loop: mui@sunsite.informatik.rwth-aachen.de
Precedence: list
Resent-Sender: mui-request@sunsite.Informatik.RWTH-Aachen.DE
X-Lines: 23
Status: RO
Content-Type: text/plain; charset="us-ascii"
Content-Length: 512

Hello,

I wonder if anybody experienced this before:

I create a custom class whose super class is another custom class,
like this:

MyClass=MUI_CreateCustomClass(NULL,NULL,SuperClass,
    sizeof(struct MyClass_Data),MyClassDispatcher);

... and delete it like this:

MUI_DeleteCustomClass(MyClass);

This causes a memory loss of 256 Bytes each time!

It does not happen if I leave out the creation of MyClass, i.e. the
SuperClass itself does not cause any losses.

-- 
 Simon Ihmig - Ihmig@tu-harburg.d400.de